Selectable variable air volume controller

ABSTRACT

A variable air volume controller includes a communications interface and a processing circuit. The communications interface is configured to facilitate communication with an external device and building equipment. The processing circuit is configured to store a plurality of predefined, selectable-applications; receive a selection of one of the plurality of predefined, selectable-applications; and implement the selected application such that the building equipment is controlled according to the selected application.

CROSS-REFERENCE TO RELATED PATENT APPLICATION

This application is a continuation application of U.S. patentapplication Ser. No. 15/474,407 filed Mar. 30, 2017 which claims thebenefit of U.S. Provisional Patent Application No. 62/328,587, filedApr. 27, 2016, both of which are incorporated herein by reference intheir entireties.

BACKGROUND

The present disclosure relates generally to the field of variable airvolume controllers. A variable air volume (VAV) controller is, ingeneral, a controller configured to control, monitor, and manageequipment of an HVAC system in or around a building or building area.

SUMMARY

One implementation of the present disclosure is related to a variableair volume controller. The variable air volume controller includes acommunications interface and a processing circuit. The communicationsinterface is configured to facilitate communication with an externaldevice and building equipment. The processing circuit is configured tostore a plurality of predefined, selectable-applications; receive aselection of one of the plurality of predefined,selectable-applications; and implement the selected application suchthat the building equipment is controlled according to the selectedapplication.

Another implementation of the present disclosure is related to abuilding management system. The building management system includesbuilding equipment and a controller coupled to the building equipment.The controller is configured to store a plurality of predefined,selectable-applications; receive a selection of one of the plurality ofpredefined, selectable-applications; and implement the selectedapplication such that the building equipment is controlled according tothe selected application.

Still another implementation of the present disclosure is related to avariable air volume controller. The variable air volume controllerincludes a communications interface and a processing circuit. Thecommunications interface is configured to facilitate communication withat least one of an external device and building equipment. Theprocessing circuit is configured to store a super-application includinga plurality of sub-applications and activate one or more of thesub-applications based on at least one of (i) receiving configurationsettings from the external device and (ii) automatically detecting atype of the building equipment connected therewith.

Those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the devices and/orprocesses described herein, as defined solely by the claims, will becomeapparent in the detailed description set forth herein and taken inconjunction with the accompanying drawings.

BRIEF DESILICON CONTROLLED RECTIFIERIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a building managementsystem (BMS) and a HVAC system, according to some embodiments.

FIG. 2 is a schematic of a waterside system which can be used as part ofthe HVAC system of FIG. 1, according to some embodiments.

FIG. 3 is a block diagram of an airside system which can be used as partof the HVAC system of FIG. 1, according to some embodiments.

FIG. 4 is a block diagram of a Building Management System (BMS) whichcan be used in the building of FIG. 1, according to some embodiments.

FIG. 5 is a block diagram of a VAV controller, according to someembodiments.

FIG. 6 is an illustration of communication between the VAV controller ofFIG. 5 and a balancing tool, according to some embodiments.

FIGS. 7A-7D are various illustrations of graphical user interfaces(GUIs) of the balancing tool of FIG. 6, according to some embodiments.

FIG. 8 is an illustration of communication between the VAV controller ofFIG. 5 and a mobile device, according to some embodiments.

DETAILED DESILICON CONTROLLED RECTIFIERIPTION

Building Management System and HVAC System

Referring now to FIGS. 1-4, an exemplary building management system(BMS) and HVAC system in which a VAV controller of the presentdisclosure can be implemented are shown, according to an exemplaryembodiment. Referring particularly to FIG. 1, a perspective view of abuilding 10 is shown. Building 10 is served by a BMS. A BMS is, ingeneral, a system of devices configured to control, monitor, and manageequipment in or around a building or building area. A BMS can include,for example, an HVAC system, a security system, a lighting system, afire alerting system, any other system that is capable of managingbuilding functions or devices, or any combination thereof.

The BMS that serves building 10 includes an HVAC system 100. HVAC system100 can include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.)configured to provide heating, cooling, ventilation, or other servicesfor building 10. For example, HVAC system 100 is shown to include awaterside system 120 and an airside system 130. Waterside system 120 canprovide a heated or chilled fluid to an air handling unit of airsidesystem 130. Airside system 130 can use the heated or chilled fluid toheat or cool an airflow provided to building 10. An exemplary watersidesystem and airside system which can be used in HVAC system 100 aredescribed in greater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and arooftop air handling unit (RTU) 106. Waterside system 120 can use boiler104 and chiller 102 to heat or cool a working fluid (e.g., water,glycol, etc.) and can circulate the working fluid to RTU 106. In variousembodiments, the HVAC devices of waterside system 120 can be located inor around building 10 (as shown in FIG. 1) or at an offsite locationsuch as a central plant (e.g., a chiller plant, a steam plant, a heatplant, etc.). The working fluid can be heated in boiler 104 or cooled inchiller 102, depending on whether heating or cooling is required inbuilding 10. Boiler 104 can add heat to the circulated fluid, forexample, by burning a combustible material (e.g., natural gas) or usingan electric heating element. Chiller 102 can place the circulated fluidin a heat exchange relationship with another fluid (e.g., a refrigerant)in a heat exchanger (e.g., an evaporator) to absorb heat from thecirculated fluid. The working fluid from chiller 102 and/or boiler 104can be transported to RTU 106 via piping 108.

RTU 106 can place the working fluid in a heat exchange relationship withan airflow passing through RTU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow can be, for example,outside air, return air from within building 10, or a combination ofboth. RTU 106 can transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, RTU106 can include one or more fans or blowers configured to pass theairflow over or through a heat exchanger containing the working fluid.The working fluid can then return to chiller 102 or boiler 104 viapiping 110.

Airside system 130 can deliver the airflow supplied by RTU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and canprovide return air from building 10 to RTU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple local airhandling units (AHUs) 116 positioned within building 10. The AHUs 116may include various components similar to the RTU 106. In someembodiments, the airside system 130 includes variable air volume (VAV)units 150. For example, airside system 130 is shown to include aseparate VAV unit 150 on each floor or zone of building 10. VAV units150 can include dampers or other flow control elements that can beoperated to control an amount of the supply airflow provided toindividual zones of building 10. In other embodiments, airside system130 delivers the supply airflow into one or more zones of building 10(e.g., via supply ducts 112) without using intermediate VAV units 150 orother flow control elements. RTU 106 and/or AHUs 116 can include varioussensors (e.g., temperature sensors, pressure sensors, etc.) configuredto measure attributes of the supply airflow. RTU 106 and/or AHUs 116 canreceive input from sensors located within RTU 106 and/or AHUs 116 and/orwithin the building zone and can adjust the flow rate, temperature, orother attributes of the supply airflow through RTU 106 and/or AHUs 116to achieve setpoint conditions for the building zone.

Referring now to FIG. 2, a block diagram of a waterside system 200 isshown, according to an exemplary embodiment. In various embodiments,waterside system 200 can supplement or replace waterside system 120 inHVAC system 100 or can be implemented separate from HVAC system 100.When implemented in HVAC system 100, waterside system 200 can include asubset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller102, pumps, valves, etc.) and can operate to supply a heated or chilledfluid to RTU 106 and/or AHUs 116. The HVAC devices of waterside system200 can be located within building 10 (e.g., as components of watersidesystem 120) or at an offsite location such as a central plant.

In FIG. 2, waterside system 200 is shown as a central plant having aplurality of subplants 202-212. Subplants 202-212 are shown to include aheater subplant 202, a heat recovery chiller subplant 204, a chillersubplant 206, a cooling tower subplant 208, a hot thermal energy storage(TES) subplant 210, and a cold thermal energy storage (TES) subplant212. Subplants 202-212 consume resources (e.g., water, natural gas,electricity, etc.) from utilities to serve the thermal energy loads(e.g., hot water, cold water, heating, cooling, etc.) of a building orcampus. For example, heater subplant 202 can be configured to heat waterin a hot water loop 214 that circulates the hot water between heatersubplant 202 and building 10. Chiller subplant 206 can be configured tochill water in a cold water loop 216 that circulates the cold waterbetween chiller subplant 206 and building 10. Heat recovery chillersubplant 204 can be configured to transfer heat from cold water loop 216to hot water loop 214 to provide additional heating for the hot waterand additional cooling for the cold water. Condenser water loop 218 canabsorb heat from the cold water in chiller subplant 206 and reject theabsorbed heat in cooling tower subplant 208 or transfer the absorbedheat to hot water loop 214. Hot TES subplant 210 and cold TES subplant212 can store hot and cold thermal energy, respectively, for subsequentuse.

Hot water loop 214 and cold water loop 216 can deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., RTU 106) or to individual floors or zones of building 10 (e.g.,AHUs 116, VAV units 150). The air handlers push air past heat exchangers(e.g., heating coils or cooling coils) through which the water flows toprovide heating or cooling for the air. The heated or cooled air can bedelivered to individual zones of building 10 to serve the thermal energyloads of building 10. The water then returns to subplants 202-212 toreceive further heating or cooling.

Although subplants 202-212 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO2, etc.) can be used inplace of or in addition to water to serve the thermal energy loads. Inother embodiments, subplants 202-212 can provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to waterside system 200are within the teachings of the present invention.

Each of subplants 202-212 can include a variety of equipment configuredto facilitate the functions of the subplant. For example, heatersubplant 202 is shown to include a plurality of heating elements 220(e.g., boilers, electric heaters, etc.) configured to add heat to thehot water in hot water loop 214. Heater subplant 202 is also shown toinclude several pumps 222 and 224 configured to circulate the hot waterin hot water loop 214 and to control the flow rate of the hot waterthrough individual heating elements 220. Chiller subplant 206 is shownto include a plurality of chillers 232 configured to remove heat fromthe cold water in cold water loop 216. Chiller subplant 206 is alsoshown to include several pumps 234 and 236 configured to circulate thecold water in cold water loop 216 and to control the flow rate of thecold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality ofheat recovery heat exchangers 226 (e.g., refrigeration circuits)configured to transfer heat from cold water loop 216 to hot water loop214. Heat recovery chiller subplant 204 is also shown to include severalpumps 228 and 230 configured to circulate the hot water and/or coldwater through heat recovery heat exchangers 226 and to control the flowrate of the water through individual heat recovery heat exchangers 226.Cooling tower subplant 208 is shown to include a plurality of coolingtowers 238 configured to remove heat from the condenser water incondenser water loop 218. Cooling tower subplant 208 is also shown toinclude several pumps 240 configured to circulate the condenser water incondenser water loop 218 and to control the flow rate of the condenserwater through individual cooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 configuredto store the hot water for later use. Hot TES subplant 210 can alsoinclude one or more pumps or valves configured to control the flow rateof the hot water into or out of hot TES tank 242. Cold TES subplant 212is shown to include cold TES tanks 244 configured to store the coldwater for later use. Cold TES subplant 212 can also include one or morepumps or valves configured to control the flow rate of the cold waterinto or out of cold TES tanks 244.

In some embodiments, one or more of the pumps in waterside system 200(e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines inwaterside system 200 include an isolation valve associated therewith.Isolation valves can be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in watersidesystem 200. In various embodiments, waterside system 200 can includemore, fewer, or different types of devices and/or subplants based on theparticular configuration of waterside system 200 and the types of loadsserved by waterside system 200.

Referring now to FIG. 3, a block diagram of an airside system 300 isshown, according to an exemplary embodiment. In various embodiments,airside system 300 can supplement or replace airside system 130 in HVACsystem 100 or can be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, airside system 300 can include a subsetof the HVAC devices in HVAC system 100 (e.g., RTU 106, AHUs 116, VAVunits 150, ducts 112-114, fans, dampers, etc.) and can be located in oraround building 10. Airside system 300 can operate to heat or cool anairflow provided to building 10 using a heated or chilled fluid providedby waterside system 200.

In FIG. 3, airside system 300 is shown to include an economizer-type airhandling unit (AHU) 302. Economizer-type AHUs vary the amount of outsideair and return air used by the air handling unit for heating or cooling.For example, AHU 302 can receive return air 304 from building zone 306via return air duct 308 and can deliver supply air 310 to building zone306 via supply air duct 312. In some embodiments, AHU 302 is a rooftopunit located on the roof of building 10 (e.g., RTU 106 as shown inFIG. 1) or otherwise positioned to receive both return air 304 andoutside air 314 (e.g., AHUs 116 as shown in FIG. 1). AHU 302 can beconfigured to operate exhaust air damper 316, mixing damper 318, andoutside air damper 320 to control an amount of outside air 314 andreturn air 304 that combine to form supply air 310. Any return air 304that does not pass through mixing damper 318 can be exhausted from AHU302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 can be operated by an actuator. For example,exhaust air damper 316 can be operated by actuator 324, mixing damper318 can be operated by actuator 326, and outside air damper 320 can beoperated by actuator 328. Actuators 324-328 can communicate with an AHUcontroller 330 via a communications link 332. Actuators 324-328 canreceive control signals from AHU controller 330 and can provide feedbacksignals to AHU controller 330. Feedback signals can include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators324-328), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat can be collected, stored, or used by actuators 324-328. AHUcontroller 330 can be an economizer controller configured to use one ormore control algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 324-328.

Still referring to FIG. 3, AHU 302 is shown to include a cooling coil334, a heating coil 336, and a fan 338 positioned within supply air duct312. Fan 338 can be configured to force supply air 310 through coolingcoil 334 and/or heating coil 336 and provide supply air 310 to buildingzone 306. AHU controller 330 can communicate with fan 338 viacommunications link 340 to control a flow rate of supply air 310. Insome embodiments, AHU controller 330 controls an amount of heating orcooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 can receive a chilled fluid from waterside system 200(e.g., from cold water loop 216) via piping 342 and can return thechilled fluid to waterside system 200 via piping 344. Valve 346 can bepositioned along piping 342 or piping 344 to control a flow rate of thechilled fluid through cooling coil 334. In some embodiments, coolingcoil 334 includes multiple stages of cooling coils that can beindependently activated and deactivated (e.g., by AHU controller 330, byBMS controller 366, etc.) to modulate an amount of cooling applied tosupply air 310.

Heating coil 336 can receive a heated fluid from waterside system 200(e.g., from hot water loop 214) via piping 348 and can return the heatedfluid to waterside system 200 via piping 350. Valve 352 can bepositioned along piping 348 or piping 350 to control a flow rate of theheated fluid through heating coil 336. In some embodiments, heating coil336 includes multiple stages of heating coils that can be independentlyactivated and deactivated (e.g., by AHU controller 330, by BMScontroller 366, etc.) to modulate an amount of heating applied to supplyair 310.

Each of valves 346 and 352 can be controlled by an actuator. Forexample, valve 346 can be controlled by actuator 354 and valve 352 canbe controlled by actuator 356. Actuators 354-356 can communicate withAHU controller 330 via communications links 358-360. Actuators 354-356can receive control signals from AHU controller 330 and can providefeedback signals to controller 330. In some embodiments, AHU controller330 receives a measurement of the supply air temperature from atemperature sensor 362 positioned in supply air duct 312 (e.g.,downstream of cooling coil 334 and/or heating coil 336). AHU controller330 can also receive a measurement of the temperature of building zone306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 viaactuators 354-356 to modulate an amount of heating or cooling providedto supply air 310 (e.g., to achieve a setpoint temperature for supplyair 310 or to maintain the temperature of supply air 310 within asetpoint temperature range). The positions of valves 346 and 352 affectthe amount of heating or cooling provided to supply air 310 by coolingcoil 334 or heating coil 336 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU controller 330can control the temperature of supply air 310 and/or building zone 306by activating or deactivating coils 334-336, adjusting a speed of fan338, or a combination of both.

Still referring to FIG. 3, airside system 300 is shown to include abuilding management system (BMS) controller 366 and a client device 368.BMS controller 366 can include one or more computer systems (e.g.,servers, supervisory controllers, subsystem controllers, etc.) thatserve as system level controllers, application or data servers, headnodes, or master controllers for airside system 300, waterside system200, HVAC system 100, and/or other controllable systems that servebuilding 10. BMS controller 366 can communicate with multiple downstreambuilding systems or subsystems (e.g., HVAC system 100, a securitysystem, a lighting system, waterside system 200, etc.) via acommunications link 370 according to like or disparate protocols (e.g.,LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMScontroller 366 can be separate (as shown in FIG. 3) or integrated. In anintegrated implementation, AHU controller 330 can be a software moduleconfigured for execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMScontroller 366 (e.g., commands, setpoints, operating boundaries, etc.)and provides information to BMS controller 366 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 330 can provide BMScontroller 366 with temperature measurements from temperature sensors362-364, equipment on/off states, equipment operating capacities, and/orany other information that can be used by BMS controller 366 to monitoror control a variable state or condition within building zone 306.

Client device 368 can include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Client device 368 can be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Client device 368 can be a stationary terminal or amobile device. For example, client device 368 can be a desktop computer,a computer server with a user interface, a laptop computer, a tablet, asmartphone, a PDA, or any other type of mobile or non-mobile device.Client device 368 can communicate with BMS controller 366 and/or AHUcontroller 330 via communications link 372.

Referring now to FIG. 4, a block diagram of a building management system(BMS) 400 is shown, according to an exemplary embodiment. BMS 400 can beimplemented in building 10 to automatically monitor and control variousbuilding functions. BMS 400 is shown to include BMS controller 366 and aplurality of building subsystems 428. Building subsystems 428 are shownto include a building electrical subsystem 434, an informationcommunication technology (ICT) subsystem 436, a security subsystem 438,a HVAC subsystem 440, a lighting subsystem 442, a lift/escalatorssubsystem 432, and a fire safety subsystem 430. In various embodiments,building subsystems 428 can include fewer, additional, or alternativesubsystems. For example, building subsystems 428 can also oralternatively include a refrigeration subsystem, an advertising orsignage subsystem, a cooking subsystem, a vending subsystem, a printeror copy service subsystem, or any other type of building subsystem thatuses controllable equipment and/or sensors to monitor or controlbuilding 10. In some embodiments, building subsystems 428 includewaterside system 200 and/or airside system 300, as described withreference to FIGS. 2-3.

Each of building subsystems 428 can include any number of devices,controllers, and connections for completing its individual functions andcontrol activities. HVAC subsystem 440 can include many of the samecomponents as HVAC system 100, as described with reference to FIGS. 1-3.For example, HVAC subsystem 440 can include a chiller, a boiler, anynumber of air handling units, economizers, field controllers (e.g., VAVcontrollers, etc.), supervisory controllers, actuators, temperaturesensors, and other devices for controlling the temperature, humidity,airflow, or other variable conditions within building 10. Lightingsubsystem 442 can include any number of light fixtures, ballasts,lighting sensors, dimmers, or other devices configured to controllablyadjust the amount of light provided to a building space. Securitysubsystem 438 can include occupancy sensors, video surveillance cameras,digital video recorders, video processing servers, intrusion detectiondevices, access control devices (e.g., card access, etc.) and servers,or other security-related devices.

Still referring to FIG. 4, BMS controller 366 is shown to include acommunications interface 407 and a BMS interface 409. Interface 407 canfacilitate communications between BMS controller 366 and externalapplications (e.g., monitoring and reporting applications 422,enterprise control applications 426, remote systems and applications444, applications residing on client devices 448, etc.) for allowinguser control, monitoring, and adjustment to BMS controller 366 and/orsubsystems 428. Interface 407 can also facilitate communications betweenBMS controller 366 and client devices 448. BMS interface 409 canfacilitate communications between BMS controller 366 and buildingsubsystems 428 (e.g., HVAC, lighting security, lifts, powerdistribution, business, etc.).

Interfaces 407, 409 can be or include wired or wireless communicationsinterfaces (e.g., jacks, antennas, transmitters, receivers,transceivers, wire terminals, etc.) for conducting data communicationswith building subsystems 428 or other external systems or devices. Invarious embodiments, communications via interfaces 407, 409 can bedirect (e.g., local wired or wireless communications) or via acommunications network 446 (e.g., a WAN, the Internet, a cellularnetwork, etc.). For example, interfaces 407, 409 can include an Ethernetcard and port for sending and receiving data via an Ethernet-basedcommunications link or network. In another example, interfaces 407, 409can include a Wi-Fi transceiver for communicating via a wirelesscommunications network. In another example, one or both of interfaces407, 409 can include cellular or mobile phone communicationstransceivers. In one embodiment, communications interface 407 is a powerline communications interface and BMS interface 409 is an Ethernetinterface. In other embodiments, both communications interface 407 andBMS interface 409 are Ethernet interfaces or are the same Ethernetinterface.

Still referring to FIG. 4, BMS controller 366 is shown to include aprocessing circuit 404 including a processor 406 and memory 408.Processing circuit 404 can be communicably connected to BMS interface409 and/or communications interface 407 such that processing circuit 404and the various components thereof can send and receive data viainterfaces 407, 409. Processor 406 can be implemented as a generalpurpose processor, an application specific integrated circuit (ASIC),one or more field programmable gate arrays (FPGAs), a group ofprocessing components, or other suitable electronic processingcomponents.

Memory 408 (e.g., memory, memory unit, storage device, etc.) can includeone or more devices (e.g., RAM, ROM, Flash memory, hard disk storage,etc.) for storing data and/or computer code for completing orfacilitating the various processes, layers and modules described in thepresent application. Memory 408 can be or include volatile memory ornon-volatile memory. Memory 408 can include database components, objectcode components, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present application. According to anexemplary embodiment, memory 408 is communicably connected to processor406 via processing circuit 404 and includes computer code for executing(e.g., by processing circuit 404 and/or processor 406) one or moreprocesses described herein.

In some embodiments, BMS controller 366 is implemented within a singlecomputer (e.g., one server, one housing, etc.). In various otherembodiments BMS controller 366 can be distributed across multipleservers or computers (e.g., that can exist in distributed locations).Further, while FIG. 4 shows applications 422 and 426 as existing outsideof BMS controller 366, in some embodiments, applications 422 and 426 canbe hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 is shown to include an enterpriseintegration layer 410, an automated measurement and validation (AM&V)layer 412, a demand response (DR) layer 414, a fault detection anddiagnostics (FDD) layer 416, an integrated control layer 418, and abuilding subsystem integration layer 420. Layers 410-420 can beconfigured to receive inputs from building subsystems 428 and other datasources, determine optimal control actions for building subsystems 428based on the inputs, generate control signals based on the optimalcontrol actions, and provide the generated control signals to buildingsubsystems 428. The following paragraphs describe some of the generalfunctions performed by each of layers 410-420 in BMS 400.

Enterprise integration layer 410 can be configured to serve clients orlocal applications with information and services to support a variety ofenterprise-level applications. For example, enterprise controlapplications 426 can be configured to provide subsystem-spanning controlto a graphical user interface (GUI) or to any number of enterprise-levelbusiness applications (e.g., accounting systems, user identificationsystems, etc.). Enterprise control applications 426 can also oralternatively be configured to provide configuration GUIs forconfiguring BMS controller 366. In yet other embodiments, enterprisecontrol applications 426 can work with layers 410-420 to optimizebuilding performance (e.g., efficiency, energy use, comfort, or safety)based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 can be configured to managecommunications between BMS controller 366 and building subsystems 428.For example, building subsystem integration layer 420 can receive sensordata and input signals from building subsystems 428 and provide outputdata and control signals to building subsystems 428. Building subsystemintegration layer 420 can also be configured to manage communicationsbetween building subsystems 428. Building subsystem integration layer420 translate communications (e.g., sensor data, input signals, outputsignals, etc.) across a plurality of multi-vendor/multi-protocolsystems.

Demand response layer 414 can be configured to optimize resource usage(e.g., electricity use, natural gas use, water use, etc.) and/or themonetary cost of such resource usage in response to satisfy the demandof building 10. The optimization can be based on time-of-use prices,curtailment signals, energy availability, or other data received fromutility providers, distributed energy generation systems 424, fromenergy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or fromother sources. Demand response layer 414 can receive inputs from otherlayers of BMS controller 366 (e.g., building subsystem integration layer420, integrated control layer 418, etc.). The inputs received from otherlayers can include environmental or sensor inputs such as temperature,carbon dioxide levels, relative humidity levels, air quality sensoroutputs, occupancy sensor outputs, room schedules, and the like. Theinputs can also include inputs such as electrical use (e.g., expressedin kWh), thermal load measurements, pricing information, projectedpricing, smoothed pricing, curtailment signals from utilities, and thelike.

According to an exemplary embodiment, demand response layer 414 includescontrol logic for responding to the data and signals it receives. Theseresponses can include communicating with the control algorithms inintegrated control layer 418, changing control strategies, changingsetpoints, or activating/deactivating building equipment or subsystemsin a controlled manner. Demand response layer 414 can also includecontrol logic configured to determine when to utilize stored energy. Forexample, demand response layer 414 can determine to begin using energyfrom energy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a control moduleconfigured to actively initiate control actions (e.g., automaticallychanging setpoints) which minimize energy costs based on one or moreinputs representative of or based on demand (e.g., price, a curtailmentsignal, a demand level, etc.). In some embodiments, demand responselayer 414 uses equipment models to determine an optimal set of controlactions. The equipment models can include, for example, thermodynamicmodels describing the inputs, outputs, and/or functions performed byvarious sets of building equipment. Equipment models can representcollections of building equipment (e.g., subplants, chiller arrays,etc.) or individual devices (e.g., individual chillers, heaters, pumps,etc.).

Demand response layer 414 can further include or draw upon one or moredemand response policy definitions (e.g., databases, XML files, etc.).The policy definitions can be edited or adjusted by a user (e.g., via agraphical user interface) so that the control actions initiated inresponse to demand inputs can be tailored for the user's application,desired comfort level, particular building equipment, or based on otherconcerns. For example, the demand response policy definitions canspecify which equipment can be turned on or off in response toparticular demand inputs, how long a system or piece of equipment shouldbe turned off, what setpoints can be changed, what the allowable setpoint adjustment range is, how long to hold a high demand setpointbefore returning to a normally scheduled setpoint, how close to approachcapacity limits, which equipment modes to utilize, the energy transferrates (e.g., the maximum rate, an alarm rate, other rate boundaryinformation, etc.) into and out of energy storage devices (e.g., thermalstorage tanks, battery banks, etc.), and when to dispatch on-sitegeneration of energy (e.g., via fuel cells, a motor generator set,etc.).

Integrated control layer 418 can be configured to use the data input oroutput of building subsystem integration layer 420 and/or demandresponse layer 414 to make control decisions. Due to the subsystemintegration provided by building subsystem integration layer 420,integrated control layer 418 can integrate control activities of thesubsystems 428 such that the subsystems 428 behave as a singleintegrated supersystem. In an exemplary embodiment, integrated controllayer 418 includes control logic that uses inputs and outputs from aplurality of building subsystems to provide greater comfort and energysavings relative to the comfort and energy savings that separatesubsystems could provide alone. For example, integrated control layer418 can be configured to use an input from a first subsystem to make anenergy-saving control decision for a second subsystem. Results of thesedecisions can be communicated back to building subsystem integrationlayer 420.

Integrated control layer 418 is shown to be logically below demandresponse layer 414. Integrated control layer 418 can be configured toenhance the effectiveness of demand response layer 414 by enablingbuilding subsystems 428 and their respective control loops to becontrolled in coordination with demand response layer 414. Thisconfiguration may advantageously reduce disruptive demand responsebehavior relative to conventional systems. For example, integratedcontrol layer 418 can be configured to assure that a demandresponse-driven upward adjustment to the setpoint for chilled watertemperature (or another component that directly or indirectly affectstemperature) does not result in an increase in fan energy (or otherenergy used to cool a space) that would result in greater total buildingenergy use than was saved at the chiller.

Integrated control layer 418 can be configured to provide feedback todemand response layer 414 so that demand response layer 414 checks thatconstraints (e.g., temperature, lighting levels, etc.) are properlymaintained even while demanded load shedding is in progress. Theconstraints can also include setpoint or sensed boundaries relating tosafety, equipment operating limits and performance, comfort, fire codes,electrical codes, energy codes, and the like. Integrated control layer418 is also logically below fault detection and diagnostics layer 416and automated measurement and validation layer 412. Integrated controllayer 418 can be configured to provide calculated inputs (e.g.,aggregations) to these higher levels based on outputs from more than onebuilding subsystem.

Automated measurement and validation (AM&V) layer 412 can be configuredto verify that control strategies commanded by integrated control layer418 or demand response layer 414 are working properly (e.g., using dataaggregated by AM&V layer 412, integrated control layer 418, buildingsubsystem integration layer 420, FDD layer 416, or otherwise). Thecalculations made by AM&V layer 412 can be based on building systemenergy models and/or equipment models for individual BMS devices orsubsystems. For example, AM&V layer 412 can compare a model-predictedoutput with an actual output from building subsystems 428 to determinean accuracy of the model.

Fault detection and diagnostics (FDD) layer 416 can be configured toprovide on-going fault detection for building subsystems 428, buildingsubsystem devices (i.e., building equipment), and control algorithmsused by demand response layer 414 and integrated control layer 418. FDDlayer 416 can receive data inputs from integrated control layer 418,directly from one or more building subsystems or devices, or fromanother data source. FDD layer 416 can automatically diagnose andrespond to detected faults. The responses to detected or diagnosedfaults can include providing an alert message to a user, a maintenancescheduling system, or a control algorithm configured to attempt torepair the fault or to work-around the fault.

FDD layer 416 can be configured to output a specific identification ofthe faulty component or cause of the fault (e.g., loose damper linkage)using detailed subsystem inputs available at building subsystemintegration layer 420. In other exemplary embodiments, FDD layer 416 isconfigured to provide “fault” events to integrated control layer 418which executes control strategies and policies in response to thereceived fault events. According to an exemplary embodiment, FDD layer416 (or a policy executed by an integrated control engine or businessrules engine) can shut-down systems or direct control activities aroundfaulty devices or systems to reduce energy waste, extend equipment life,or assure proper control response.

FDD layer 416 can be configured to store or access a variety ofdifferent system data stores (or data points for live data). FDD layer416 can use some content of the data stores to identify faults at theequipment level (e.g., specific chiller, specific AHU, specific terminalunit, etc.) and other content to identify faults at component orsubsystem levels. For example, building subsystems 428 can generatetemporal (i.e., time-series) data indicating the performance of BMS 400and the various components thereof. The data generated by buildingsubsystems 428 can include measured or calculated values that exhibitstatistical characteristics and provide information about how thecorresponding system or process (e.g., a temperature control process, aflow control process, etc.) is performing in terms of error from itssetpoint. These processes can be examined by FDD layer 416 to exposewhen the system begins to degrade in performance and alert a user torepair the fault before it becomes more severe.

Variable Air Volume Controller

Referring now to FIGS. 5-8, a controller, shown as variable air volumefield (VAV) controller 500, and various programmer devices 530 areshown, according to various exemplary embodiments. In some embodiments,VAV controller 500 is configurable, but not fully programmable. Inalternative embodiments, the VAV controller 500 is fully programmable.VAV controller 500 may be usable with BMS 400. Traditional VAV fieldcontrollers may be fully programmable, making them very flexible.However, this flexibility may also make them complex to use. A complextool (e.g., a Controller Configuration Tool (CCT), a ProgrammableConfiguration Tool (PCT), a personal computer based tool, etc.) is oftenrequired to build desired applications for the VAV field controllers tooperate various building equipment (e.g., HVAC systems and equipmentthereof, etc.). This programmability also requires (i) time to build theapplications, (ii) time to customize the applications as needed, (iii)time to download the applications to the VAV field controllers from thecomplex tool on a job site, and (iv) time to test and verify anycustomizations made to the applications. All this time to programtraditional VAV field controllers costs money, which may be saved byusing one or more pre-defined, pre-loaded applications on the VAVcontroller 500 (e.g., rather than custom building the applications eachtime, etc.). In some embodiments, the controller is structured asanother type of controller other than a VAV controller (e.g., an airhandling unit controller, a fan coil unit controller, etc.).

As shown in FIG. 5, the VAV controller 500 includes a communicationsinterface 520. The communications interface 520 may include wired orwireless interfaces (e.g., jacks, antennas, transmitters, receivers,transceivers, wire terminals, etc.) for conducting data communicationswith various systems, devices, or networks. For example, thecommunications interface 520 may include an Ethernet card and port forsending and receiving data via an Ethernet-based communications networkand/or a WiFi transceiver for communicating via a wirelesscommunications network. The communications interface 520 may beconfigured to communicate via local area networks or wide area networks(e.g., the Internet, a building WAN, etc.) and may use a variety ofcommunications protocols (e.g., BACnet, IP, LON, Bluetooth, ZigBee,radio, cellular, etc.).

The communications interface 520 of the VAV controller 500 mayfacilitate communicating with a programmer device 530, a CCT/PCT device570, and/or HVAC components 580 (e.g., building equipment similar to thecomponents of HVAC system 100, airside system 300, etc.). Communicationbetween and among the VAV controller 500 and the programmer device 530,the CCT/PCT device 570, and/or the HVAC components 580 may be via anynumber of wired or wireless connections (e.g., any standard under IEEE802, etc.). For example, a wired connection may include a serial cable,a fiber optic cable, a CAT5 cable, or any other form of wiredconnection. In comparison, a wireless connection may include theInternet, Wi-Fi, cellular, Bluetooth, ZigBee, radio, BACnet, etc. In oneembodiment, a controller area network (CAN) bus provides the exchange ofsignals, information, and/or data. The CAN bus can include any number ofwired and wireless connections that provide the exchange of signals,information, and/or data. The CAN bus may include a local area network(LAN), or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider).

According to an exemplary embodiment, the VAV controller 500 is aselectable VAV controller for VAV box applications, and does not requireany software tools (e.g., a CCT, a PCT, etc.) to initiate the propersequence of operation to control the HVAC components 580. By way ofexample, a plurality of predefined applications (e.g., twenty, fifteen,twenty-five, etc.) may be downloaded and stored within a memory of theVAV controller 500 (e.g., by the manufacturer, to cover over 90% of allpossible system configurations, etc.). A desired application may then beselected in the field from the plurality of predefined applicationsusing the programmer device 530 (e.g., a portable device, a smartphone,a tablet, a laptop, a VAV Balancing Tool, etc.). In addition toselecting the desired application, the programmer device 530 may beconfigured to facilitate changing application parameters. Having adesired application selected in the field without the need for asoftware tool (e.g., the CCT/PCT device 570, etc.) may result inimproved workflows and a significant installation cost savingsopportunity. Additionally, this may allow the installer to select thefield-selectable application, thus allowing technicians to work onother, more value-added activities. Additional applications, beyond theplurality of applications that are predefined within the memory of theVAV controller 500, may be added via the CCT/PCT device 570 (e.g., forcases where the plurality of predefined applications do not meet thefield requirement, etc.).

As shown in FIG. 5, the function and structure of the VAV controller 500is shown according to an example embodiment. The VAV controller 500 isshown to include a processing circuit 502 including a processor 504 anda memory 506. The processor 504 may be implemented as a general-purposeprocessor, an application specific integrated circuit (ASIC), one ormore field programmable gate arrays (FPGAs), a digital signal processor(DSP), a group of processing components, or other suitable electronicprocessing components. The memory 506 (e.g., NVRAM, RAM, ROM, FlashMemory, hard disk storage, etc.) may store data and/or computer code forfacilitating the various processes described herein. Thus, the memory506 may be communicably connected to the processor 504 and providecomputer code or instructions to the processor 504 for executing theprocesses described in regard to the VAV controller 500 herein.Moreover, the memory 506 may be or include tangible, non-transientvolatile memory or non-volatile memory. Accordingly, the memory 506 mayinclude database components, object code components, script components,or any other type of information structure for supporting the variousactivities and information structures described herein.

The memory 506 is shown to include various modules for completing theactivities described herein. More particularly, the memory 506 includesa communication module 508, an application module 510, and a controlmodule 512. The modules 508-512 may be configured to receive a selectionof an application of the VAV controller 500 to implement to facilitatecontrolling operation of various building components (e.g., HVAC systemcomponents, etc.). While various modules with particular functionalityare shown in FIG. 5, it should be understood that the VAV controller 500and the memory 506 may include any number of modules for completing thefunctions described herein. For example, the activities of multiplemodules may be combined as a single module, as additional modules withadditional functionality may be included, etc. Further, it should beunderstood that the VAV controller 500 may further control otheractivity beyond the scope of the present disclosure.

The communications module 508 may be configured to send and receiveinformation (e.g., data, commands, etc.) between the VAV controller 500and the programmer device 530, the CCT/PCT device 570, and/or the HVACcomponents 580. Thus, the communication module 508 may be communicablyand/or operatively coupled with the communications interface 520. Insome embodiments, the communications module 508 is configured tofacilitate receiving an application selection from the programmer device530. The communications module 508 may then transmit the applicationselection to the application module 510 to take further action, asdescribed further herein. In some embodiments, the communication module508 is configured to receive a series of field configuration settings tofacilitate configuring a stored application within the applicationmodule 510. In some embodiments, the communications module 508 isconfigured to facilitate receiving a custom application from the CCT/PCTdevice 570. The communications module 508 may then transmit the customapplication to the application module 510 to take further action, asdescribed further herein. In some embodiments, the communications module508 is configured to facilitate receiving one or more modifications foran application stored within the application module 510. In someembodiments, the communication module 508 is configured to receivecommands from the control module 512 and transmit such commands to theHVAC components 580 to initiate proper operation of the HVAC components,as describe further herein.

The application module 510 may be configured to receive and store theplurality of predefined applications. In some embodiments, theapplication module 510 is configured to receive and store asuper-application configured to facilitate controlling a plurality ofcomponents and arrangements of the HVAC components 580. Thesuper-application may be customized through a series of fieldconfiguration settings inputted via the programmer device 530 (e.g.,based on the type of application, etc.) and/or automatically based oninformation received from HVAC components 580 (e.g., detecting whichequipment the VAV controller 500 is connected to, etc.). The applicationmodule 510 may be configured to activate and/or deactivate certainportions of the super-application (e.g., sub-applications thereof, etc.)based on (i) the field configuration setting received from theprogrammer device 530 (i.e., based on a manual user input) and/or (ii)based on the detected building equipment (i.e., automatically).

In some embodiments, the application module 510 is additionally oralternatively configured to receive and store a plurality of individual,predefined applications. According to an exemplary embodiment, theplurality of individual, predefined applications includeselectable-applications that are relatively simple and more focused on aspecific implementation (e.g., relative to the super-application,control of a specific component or portion of the HVAC components 580,etc.). This may allow for a plurality of pre-loaded applications to bestored within the application module 510, covering a majority (e.g.,90%, etc.) of all implementations. An additional benefit of theselectable-application approach is that the set of predefinedapplications may be easily tailored for specific customers (e.g., OEMs,etc.) or markets. Using smaller, selectable applications may also allowfor increased performance of the HVAC components 580 (e.g., since aselected application is designed to operate for a single implementation,etc.) and a reduction in possible issues within the source code of theapplication (e.g., relative to a custom-built application, relative to asuper-application, etc.).

An example of possible selectable-applications stored within theapplication module 510 is shown in Table 1. The applications shown inTable 1 may apply to single duct applications (e.g., no fan, etc.), fanapplications, and/or dual duct/exhaust box applications. It should benoted that the applications of Table 1 are provided for example, andshould not be considered as limiting as other applications may bepossible.

TABLE 1 Possible Selectable-Applications Config- urable Con- App troller# Box Fan Description Single 1 Single Duct No Fan Single Duct - CoolingOnly Duct Single 2 Single Duct No Fan Single Duct with HW Reheat DuctSingle 3 Single Duct No Fan Single Duct with Electric Duct Staged ReheatSingle 4 Single Duct No Fan Single Duct with HW Duct Reheat &Supplemental Heat Fan 5 Single Duct Series Fan Series Fan with HW ReheatSingle Speed Fan 6 Single Duct Parallel Fan Parallel Fan with HW ReheatFan 7 Single Duct Series Fan Series Fan with HW Single Speed Reheat &Supplemental Heat Fan 8 Single Duct Parallel Fan Parallel Fan with HWReheat & Supplemental Heat Fan 9 Single Duct Series Fan Series Fan withElectric Single Speed Staged Reheat Fan 10 Single Duct Parallel FanParallel Fan with Electric Staged Reheat Fan 11 Single Duct Series FanSeries Fan No Heat Single Speed Fan 12 Single Duct Parallel Fan ParallelFan No Heat Fan 13 Single Duct Series Fan Series Fan with RemoteVariable ECM Speed Fan 14 Single Duct Series Fan Series Fan with RemoteVariable HW & HW Reheat Speed Fan 15 Single Duct Series Fan Series Fanwith Remote Variable ECM, HW Reheat & Speed Supplemental Heat Fan 16Single Duct Series Fan Series Fan with Remote Variable ECM & ElectricReheat Speed Single 17 Single Duct No Fan Single Duct with SCR DuctElectric Reheat Fan 18 Single Duct Series Fan Series Fan with SCR SingleSpeed Electric Reheat Fan 19 Single Duct Series Fan Series Fan withRemote Variable ECM & SCR Electric Reheat Speed Fan 20 Single DuctParallel Fan Parallel Fan with SCR Electric Reheat Dual 21 Dual Duct NoFan Dual Duct with Mixing Duct Exhaust Dual 22 Dual Duct No Fan DualDuct Constant Volume Duct Exhaust Dual 23 Exhaust No Fan Supply/ExhaustMatching Duct Damper (Supply Box) Exhaust

In some embodiments, application module 510 is configured to storemetadata that is shared between each of the selectable-applications. Byway of example, all the metadata used by VAV controller 500 may bestored by application module 510 in a shared portion of memory 506. Theshared portion of memory 506 may be accessible by each of theselectable-applications. According to an exemplary embodiment, such anarrangement facilitates providing VAV controller 500 with a smallermemory 506 relative to if metadata was segmented and stored individuallyfor each of the selectable-applications.

In some embodiments, the application module 510 is configured tofacilitate receiving and storing custom applications generated by a uservia the CCT/PCT device 570. The user may select to overwrite one or moreof the predefined applications with the custom application or store thecustom application without overwriting any of the predefinedapplications (e.g., if there is available free memory, etc.). In someembodiments, a user is able to upload, download, commission, and/ormodify one or more of the selectable-applications via the CCT/PCT device570 to create a custom application within the application module 510.

According to an exemplary embodiment, an application stored within theapplication module 510 may be selected (i) locally from a balancingtool, (ii) locally from a mobile access portal (MAP) (e.g., using amobile device, etc.), (iii) locally using a user interface (e.g., dipswitches, display, etc.) of VAV controller 500, and/or (iv) remotely(e.g., from a network automation engine (NAE) via a BACnet point, etc.).

As shown in FIGS. 6-7D, the programmer device 530 includes a balancingtool 540. According to an exemplary embodiment, the balancing tool 540is configured to facilitate selecting an application from the pluralityof pre-defined applications of the VAV controller 500. In otherembodiments, the balancing tool 540 is configured to facilitateconfiguring the super-application of the VAV controller 500. As shown inFIG. 6, the balancing tool 540 includes a dial 542, an enter button 544,a cancel/back button 546, and a display 548. The dial 542 may beconfigured to facilitate scrolling between various user interfaces ofthe balancing tool 540. The enter button 544 may be configured tofacilitate selecting a desired user interface and/or selecting a desiredapplication from the predefined applications. The cancel/back button 246may be configured to facilitate moving back to a previous user-interfaceand/or canceling a current command. The display 548 may be configured todisplay the various user interfaces.

As shown in FIGS. 7A-7D, an application of the VAV controller 500 may beselected via the balancing tool 540. As shown in FIG. 7A, a user mayadjust dial 542 to reach an info user interface 550 on the display 548.By selecting the info user interface 550 (e.g., via the enter button544, etc.), the display 548 of the balancing tool 540 displays a MSTPinterface 552 (FIG. 7B) to provide the Master-Slave/Token-Passing (MSTP)address of the VAV controller 500. As shown in FIG. 7C, the user mayadjust dial 542 to reach an application user interface 554 on thedisplay 548. By selecting the application user interface 554 (e.g., viathe enter button 544, etc.), the display 548 of the balancing tool 540displays an application selection interface 556 (FIG. 7D). Theapplication selection interface 556 is configured to display anidentifier (e.g., a number, etc.) associated with the storedselectable-applications. The user may scroll through the variousidentifiers with the dial 542 and select a desired application with theenter button 544.

As shown in FIG. 8, the programmer device 530 includes a mobile device560 (e.g., a smartphone, a tablet, a laptop, a PDA, etc.). According toan exemplary embodiment, the mobile device 560 is configured tofacilitate selecting an application from the plurality of pre-definedapplications of the VAV controller 500. In other embodiments, the mobiledevice 560 is configured to facilitate configuring the super-applicationof the VAV controller 500.

In some embodiments, a user interface of VAV controller 500 isconfigured to facilitate selecting an application from the plurality ofpre-defined applications of VAV controller 500. In other embodiments,the user interface of VAV controller 500 is configured to facilitateconfiguring the super-application of VAV controller 500. By way ofexample, the user interface of VAV controller 500 may include aplurality of switches, e.g., dip switches, used to provide an inputdirectly to VAV controller 500 to indicate which of the pre-definedapplications to implement and/or to reconfigure the super-application(e.g., activate/deactivate certain sub-applications, etc.). By way ofanother example, the user interface of VAV controller 500 may include adisplay, buttons, knobs, switches, etc. that facilitate providing aninput directly to VAV controller 500 to indicate which of thepre-defined applications to implement and/or to reconfigure thesuper-application.

Referring back to FIG. 5, the control module 512 is configured to clearthe configuration data file, reset the VAV controller 500, and use thenewly selected application during its normal startup sequence when a newapplication is selected via the programmer device 530. Thus, the controlmodule 512 may be configured to initiate the proper sequence ofoperation to control the HVAC components 580. The control module 512 maythereby send commands to the HVAC components 580 according to theselected application via the communication module 508.

Therefore, the VAV controller 500 provides a configurable controller fordirect and indirect channels that does not require any software tools(e.g., the CCT/PCT device 570, etc.) to initiate a proper sequence ofoperation. Therefore, the VAV controller 500, once leaving themanufacturing facility, is a “configurable” controller and does notrequire that the applications be built on-site. The VAV Controller 500may thereby provide multiple benefits including simplified workflows andinstallation cost savings (e.g., relative to traditional, fullyprogrammable VAV field controllers, etc.). For example, the VAVController 500 may save (i) the time previously spent building theapplications, (ii) the time previously spent customizing theapplications based on the implementation, (iii) the time spentdownloading the applications to the VAV field controllers from thecomplex tool on a job site, and (iv) the time previously spent testingand verifying any customizations made to the applications.

Configuration of Exemplary Embodiments

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements can bereversed or otherwise varied and the nature or number of discreteelements or positions can be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepscan be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions can be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure can be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps canbe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

What is claimed is:
 1. A variable air volume controller, comprising: a communications interface configured to facilitate communication with at least one of an external device and building equipment; a processing circuit configured to: store a plurality of predefined, selectable-applications; receive a selection of one of the plurality of predefined, selectable-applications, wherein the plurality of predefined, selectable-applications comprise at least two of a single duct—cooling only, single duct with hot water reheat, single duct with electric staged reheat, single duct with hot water reheat & supplemental heat, series fan with hot water reheat, parallel fan with hot water reheat, series fan with hot water reheat & supplemental heat, parallel fan with hot water reheat & supplemental heat, series fan with electric staged reheat, parallel fan with electric staged reheat, series fan no heat, parallel fan no heat, series fan with remote electronically controlled motor, series fan with remote electronically controlled motor & hot water reheat, series fan with remote electronically controlled motor, hot water reheat & supplemental heat, series fan with remote electronically controlled motor & electric reheat, single duct with silicon controlled rectifier electric reheat, series fan with silicon controlled rectifier electric reheat, series fan with remote electronically controlled motor & silicon controlled rectifier electric reheat, parallel fan with silicon controlled rectifier electric reheat, dual duct with mixing, dual duct constant volume, and supply/exhaust matching application; and implement the selected application such that the building equipment is controlled according to the selected application; and a user interface including a plurality of dip switches configured to facilitate user selection of the one of the plurality of predefined, selectable-applications by manually engaging with one or more of the plurality of dip switches associated with the one of the plurality of predefined, selectable-applications.
 2. The variable air volume controller of claim 1, wherein the building equipment includes heating, ventilation, and air conditioning components.
 3. The variable air volume controller of claim 1, wherein the external device includes at least one of a mobile device and a balancing tool.
 4. The variable air volume controller of claim 1, wherein each of the plurality of predefined, selectable-applications is focused on a specific implementation for the building equipment.
 5. The variable air volume controller of claim 1, wherein the variable air volume controller is configurable and not fully-programmable.
 6. The variable air volume controller of claim 1, wherein the processing circuit is configured to store metadata for the plurality of predefined, selectable-applications in a shared location.
 7. The variable air volume controller of claim 1, wherein the processing circuit is configured to detect the building equipment coupled therewith, and wherein the selection of the one of the plurality of predefined, selectable-applications is autonomously determined by the processing circuit based on the building equipment detected.
 8. The variable air volume controller of claim 1, wherein the plurality of predefined, selectable-applications comprise three or more of the single duct—cooling only, single duct with hot water reheat, single duct with electric staged reheat, single duct with hot water reheat & supplemental heat, series fan with hot water reheat, parallel fan with hot water reheat, series fan with hot water reheat & supplemental heat, parallel fan with hot water reheat & supplemental heat, series fan with electric staged reheat, parallel fan with electric staged reheat, series fan no heat, parallel fan no heat, series fan with remote electronically controlled motor, series fan with remote electronically controlled motor & hot water reheat, series fan with remote electronically controlled motor, hot water reheat & supplemental heat, series fan with remote electronically controlled motor & electric reheat, single duct with silicon controlled rectifier electric reheat, series fan with silicon controlled rectifier electric reheat, series fan with remote electronically controlled motor & silicon controlled rectifier electric reheat, parallel fan with silicon controlled rectifier electric reheat, dual duct with mixing, dual duct constant volume, and supply/exhaust matching application.
 9. The variable air volume controller of claim 1, wherein the plurality of predefined, selectable-applications comprise a majority of the single duct—cooling only, single duct with hot water reheat, single duct with electric staged reheat, single duct with hot water reheat & supplemental heat, series fan with hot water reheat, parallel fan with hot water reheat, series fan with hot water reheat & supplemental heat, parallel fan with hot water reheat & supplemental heat, series fan with electric staged reheat, parallel fan with electric staged reheat, series fan no heat, parallel fan no heat, series fan with remote electronically controlled motor, series fan with remote electronically controlled motor & hot water reheat, series fan with remote electronically controlled motor, hot water reheat & supplemental heat, series fan with remote electronically controlled motor & electric reheat, single duct with silicon controlled rectifier electric reheat, series fan with silicon controlled rectifier electric reheat, series fan with remote electronically controlled motor & silicon controlled rectifier electric reheat, parallel fan with silicon controlled rectifier electric reheat, dual duct with mixing, dual duct constant volume, and supply/exhaust matching application.
 10. A building management system, comprising: a controller configured to couple to building equipment, the controller configured to: store a plurality of predefined, selectable-applications; receive a selection of one of the plurality of predefined, selectable-applications, wherein the plurality of predefined, selectable-applications comprise at least two of a single duct—cooling only, single duct with hot water reheat, single duct with electric staged reheat, single duct with hot water reheat & supplemental heat, series fan with hot water reheat, parallel fan with hot water reheat, series fan with hot water reheat & supplemental heat, parallel fan with hot water reheat & supplemental heat, series fan with electric staged reheat, parallel fan with electric staged reheat, series fan no heat, parallel fan no heat, series fan with remote electronically controlled motor, series fan with remote electronically controlled motor & hot water reheat, series fan with remote electronically controlled motor, hot water reheat & supplemental heat, series fan with remote electronically controlled motor & electric reheat, single duct with silicon controlled rectifier electric reheat, series fan with silicon controlled rectifier electric reheat, series fan with remote electronically controlled motor & silicon controlled rectifier electric reheat, parallel fan with silicon controlled rectifier electric reheat, dual duct with mixing, dual duct constant volume, lighting, and supply/exhaust matching or damper supply box application; and implement the selected application such that the building equipment is controlled according to the selected application; wherein the controller includes a user interface including a plurality of dip switches configured to facilitate user selection of the one of the plurality of predefined, selectable-applications by manually engaging with one or more of the plurality of dip switches associated with the one of the plurality of predefined, selectable-applications.
 11. The building management system of claim 10, wherein the building equipment includes heating, ventilation, and air conditioning components, and wherein the controller is configured as a variable air volume controller.
 12. The building management system of claim 10, wherein each of the plurality of predefined, selectable-applications is focused on a specific implementation for the building equipment.
 13. The building management system of claim 10, wherein the controller is configurable and not fully-programmable.
 14. The building management system of claim 10, wherein the controller is configured to store metadata for the plurality of predefined, selectable-applications in a shared location.
 15. A variable air volume controller, comprising: a communications interface configured to facilitate communication with at least one of an external device and building equipment; a processing circuit configured to: store a super-application including a plurality of sub-applications; and activate one or more of the plurality of sub-applications, wherein the plurality of sub-applications comprise at least two of a single duct—cooling only, single duct with hot water reheat, single duct with electric staged reheat, single duct with hot water reheat & supplemental heat, series fan with hot water reheat, parallel fan with hot water reheat, series fan with hot water reheat & supplemental heat, parallel fan with hot water reheat & supplemental heat, series fan with electric staged reheat, parallel fan with electric staged reheat, series fan no heat, parallel fan no heat, series fan with remote electronically controlled motor, series fan with remote electronically controlled motor & hot water reheat, series fan with remote electronically controlled motor, hot water reheat & supplemental heat, series fan with remote electronically controlled motor & electric reheat, single duct with silicon controlled rectifier electric reheat, series fan with silicon controlled rectifier electric reheat, series fan with remote electronically controlled motor & silicon controlled rectifier electric reheat, parallel fan with silicon controlled rectifier electric reheat, dual duct with mixing, dual duct constant volume, and supply/exhaust matching application; and a user interface including a plurality of dip switches configured to facilitate user activation of the one or more of the plurality of sub-applications by manually engaging with one or more of the plurality of dip switches associated with the one or more of the plurality of sub-applications.
 16. The variable air volume controller of claim 15, wherein each of the plurality of sub-applications is focused on a specific implementation for the building equipment.
 17. The variable air volume controller of claim 15, wherein at least one of the plurality of sub-applications does not apply to the building equipment connected to the variable air volume controller such that the at least one of the plurality of sub-applications remains deactivated within the super-application. 